View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000617 | T99X171.00 SKB Eagle | SW Issue | public | 2019-04-11 17:11 | 2019-08-30 16:41 |
| Reporter | Assigned To | (SW) Kerwin Chen | Due Date | ||
| Priority | high | Severity | s2-severe | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0000617: BT pairing keeps failing by error code 33 | ||||
| Description | It has been encountered that BT pairing keeps failing by error code 33. [Test Procedure] 1) Make sure that BT connection is established 2) Enter the remote control & accessory menu and try to unpair BT via the menu(Unpair both RCU BT and Audio) 3) Try to pair BT via [*] + [#] and verify if RCU BT is connected again [Actual Result] Continue to be failed by error code 33. [Expected Result] BT connection must be established normally [Version] v15.502.10 | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) Jewoo Lee , (ALTech) SY Yoon , (SW) Jacky Chiang |
|---|
|
2019-04-11 17:11 developer |
|
|
|
Hi Kerwin, As verified with your test version + BT chipset A1, this issue has not been encountered in your STB. Please check if this issue could not be reproduced since your test version is different from our offical version or by BT chipset A1. For your refernce, this issue has been observed when we checked with Kaon STB, so I think it seems to be related to your test version(BT stack improvement). |
|
|
Hi Kerwin, As we already discussed, Please help to update the current progress status if you think RCU has any problem on this symptom. |
|
|
Hi Eric, Per discuss with UEI Mr. Kim, if mobile phone also can't discover RCU at the same time, that will be problem on RCU itself. I already ask UEI to check if this is a known bug or not and will update here once I get reply. |
|
|
Hi Kerwin, Could you let us know if you have any update? |
|
|
Hi Eric, We update BT CYW20704-A2 official FW from Cypress in v15.502.13. I don't see this issue on this release. Could you help to try again on this version? Thanks ! |
|
|
Hi Kerwin, This issue has been reproduced in V15.503.13 as well. The first test is OK but the error code 33 keeps occurring since the second test. The attached log has BT level 5, please check it. |
|
|
Hi Eric, There is no RCU (14:4E:34:91:0B:47, BRM_BA01_B47) related event in the log file. Do you use smart phone to scan RCU at the same time ? I think it is RCU side issue and may recover by reinstalling RCU's battery. |
|
|
Hi Kerwin, I'm on a business trip to Vietnam, so my colleague will be doing the test and updating the relevant log again. BTW, this issue has not been observed in Kaon STB, so I think you need to modify something in Eagle even though the issue has been caused by RCU. I would be grateful if you could keep checking it. |
|
|
Hi Kerwin, This issue was reproduced. Attached the additional log log name : log_keep failing by error code 33 (0425) Thank you |
|
|
|
|
|
Hi Kerwin, We have done the test again with Kaon box and the issue has been encountered in 2 ~ 3 times, it also has the same issue. As you mentioned, it seems to be RCU side's issue. So I'd like to have any evidence that it's caused by RCU's defect, could you please check it with the log that our colleage attached? Thanks for your great support at all times. |
|
|
Hi Eric, In the log file, TVS's pairing program(PairingManager) starts to scan RCU around line 17840. 04-25 14:41:50.382 4118 4118 I PairingManager: startDiscovery(), SCANNING_DEVICE ...... 04-25 14:42:15.433 4118 4118 I PairingManager: timeOutPairing() There is no RCU (MAC address is 9C:AC:6D:00:00:49) found during this period. The easiest way to have another evidence of RCU's defect is to use a smart phone scanning BT devices while doing RCU pairing. |
|
|
This ticket is too old so close it. if have some problme about it, we will create new ticket. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-04-11 17:11 |
|
New Issue | |
| 2019-04-11 17:11 |
|
Status | new => assigned |
| 2019-04-11 17:11 |
|
Assigned To | => (SW) Kerwin Chen |
| 2019-04-11 17:11 |
|
File Added: log_keep failing by error code 33.zip | |
| 2019-04-11 17:11 |
|
Issue Monitored: (ALTech) SY Yoon | |
| 2019-04-11 17:12 |
|
Issue Monitored: (ALTech) Jewoo Lee | |
| 2019-04-11 17:12 |
|
Issue Monitored: (SW) Jacky Chiang | |
| 2019-04-11 17:17 |
|
Note Added: 0001990 | |
| 2019-04-15 09:22 |
|
Note Added: 0001999 | |
| 2019-04-15 09:54 | (SW) Kerwin Chen | Note Added: 0002003 | |
| 2019-04-22 17:16 |
|
Note Added: 0002120 | |
| 2019-04-22 20:18 | (SW) Kerwin Chen | Note Added: 0002127 | |
| 2019-04-23 08:46 | (SW) Kerwin Chen | Assigned To | (SW) Kerwin Chen => (ALTech) Eric Kim |
| 2019-04-23 13:39 |
|
File Added: log.7z | |
| 2019-04-23 13:39 |
|
Note Added: 0002145 | |
| 2019-04-23 13:40 |
|
Assigned To | (ALTech) Eric Kim => (SW) Kerwin Chen |
| 2019-04-23 13:40 |
|
Description Updated | |
| 2019-04-24 13:39 | (SW) Kerwin Chen | Note Added: 0002168 | |
| 2019-04-24 22:12 |
|
Note Added: 0002187 | |
| 2019-04-25 13:48 | (ALTech) Kian Choi | Note Added: 0002195 | |
| 2019-04-25 13:48 | (ALTech) Kian Choi | Note Edited: 0002195 | |
| 2019-04-25 13:49 | (ALTech) Kian Choi | File Added: log_keep failing by error code 33 (0425).zip | |
| 2019-04-25 14:54 |
|
Note Added: 0002196 | |
| 2019-04-25 17:04 | (SW) Kerwin Chen | Note Added: 0002205 | |
| 2019-08-30 16:41 |
|
Status | assigned => closed |
| 2019-08-30 16:41 |
|
Resolution | open => fixed |
| 2019-08-30 16:41 |
|
Note Added: 0002938 |
